AMD/Intel: Switchable graphics

Hi,

Thank you for posting your query in Windows 10 Technical Preview.

For better understanding of the issue, please provide us following information:

1. What is the make and model of the computer you are facing issues with?
2. Does the issue occurs while using the default drivers provided by the manufacturer?

Do get back to us with the required information so that we can research on the issue and get back to you.

Hi ShrikarAcharya,

Thanks for the quick response.

1. My computer is an HP Envy 14 1090eo, but as you can see in the discussion every laptop with Intel HD graphics (IronLake) and either ATI Mobility Radeon 5000 series or 6000 series will show the same behavior.

2. I've tried getting the latest drivers from Windows Update and the latest drivers from Intel and AMD but they all result in a bootloop. If you read my post in the discussion you will understand that this doesn't happen with Windows 7.

The latest HP driver only support Windows 7.

If I can provide you with logs or anything that would be helpful don't hesitate to ask

Hi,

Thank you for posting your query in Windows 10 Technical Preview.

For better understanding of the issue, please provide us following information:

1. What is the make and model of the computer you are facing issues with?
2. Does the issue occurs while using the default drivers provided by the manufacturer?

Do get back to us with the required information so that we can research on the issue and get back to you.

Any update on this?

I see AMD has acknowledged the Code 43 bug but not this bug?! 

-------------------------------------------------------------------------------------------------

EDIT 4: (09/02/16)

Hello everyone,

HDMI is FIXED with Radeon Software 16.1, great!!! :D

Everyting is working with full cleanup DDU.

We made a great campaign, I am pleased that together we can solve these problems by informing Microsoft, since AMD always ignored us.

Thanks .Dalby, UnifL team, for this great campaign.

Thanks to Microsoft for forcing AMD.

Thank you all for your participation :D

Now report, if possible, about other problems with the Dynamic mode.

Regards

-------------------------------------------------------------------------------------------------

EDIT 3: (07/11/15)

Hello everyone,

I've just come from the university and installed the Catalyst 15.11, confirmed all my games work on ATI, no more black screen :D

Thanks .Dalby, UnifL team, for this great campaign.

Thanks to Microsoft for forcing AMD, and AMD to solve it.

Thank you all for your participation :D

Now wait for the official HDMI solution, and report, if possible, about other problems with the Dynamic mode.

-------------------------------------------------------------------------------------------------

EDIT 2: (05/11/15)

Hello everyone,
Guys, this issue HDMI can be resolved soon, AMD already acknowledged the problem in the Catalyst 15.11 beta:

Known Issues:

-------------------------------------------------------------------------------------------------

EDIT 1: (28/10/15)

Hello everyone,

Bootloop was already solved (Thanks to Microsoft for forcing AMD), But problems still exist with any drivers which are newer than 14.4 (By extension, any driver from Windows Update).
This post is only for Intel 1GEN + ATI variants.

To clarify, the Black screen that we are reporting is not the same black screen that appears to the login.

-->There exist two Black screen:
1. When you open certain applications ATI / AMD, these get black screen with sound. (only Intel 1gen + ATI variants)
2. Black screen (up to two minutes) after loading Windows but before logon. This is solved (temporarily) with ULPS= 0, UnifL drivers by default. (common problem for everyone Intel + AMD)

-->HDMI still not working.(only Intel 1gen + ATI variants)

Regards

PS: I'm from Spain, I used google translate.

-------------------------------------------------------------------------------------------------

(04/02/15)

Confirmed, I have a first generation Intel and ATI Radeon 5470M "Switchable Graphics".
I have 2 operating systems:
Windows 7: No problems with later drivers to Catalyst 14.4.

Windows 8.1: bootloop with later drivers to Catalyst 14.4.

This problem also exists in Windows 10, which brings me to the question:
Why has not been solved?
How much waiting to fix it?
The Catalyst 14.4 was published in April 2014, so far Microsoft and AMD do not give a solution.

How do you expect Microsoft to upgrade to Windows 10 if this problem is not solved?

This is a very serious problem, should fix this first.
As always ignored and / or leave in background Mobility users.

Also, with the build 9926 of Windows 10, we were able to install the Catalyst 14.4, but Microsoft made it impossible installation. What a shame.

PS: I'm from Spain, I used google translate.

Hi,

Thank you for providing the required information.

We are working with AMD to get the issue fixed.

You may refer to the response of Pete Levinthal from the following link for further update on the issue:

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/code-43-errors-in-device-manager-for-amd-graphics/9d752e73-70ae-4118-923d-7576dc515443?page=4

Do get back to us if you need further assistance.

Hi Von,

Code 43 is not a bug, it’s indeed an error message which stops a device to work if the device driver creates a problem or doesn't functions properly.

We are working with AMD to get this issue fixed.

Please refer to the link in above post for further update on the issue.

Hope it helps, get back to us if you need further assistance with Windows.

Same Here:

Acer 4820TG with intel core i7 640m and Amd Radeon HD 6550M

Please fix

Hi,

Thank you for providing the required information.

We are working with AMD to get the issue fixed.

You may refer to the response of Pete Levinthal from the following link for further update on the issue:

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/code-43-errors-in-device-manager-for-amd-graphics/9d752e73-70ae-4118-923d-7576dc515443?page=4

Do get back to us if you need further assistance.

Hi ShrikarAcharya,

This is not the same issue....

Please reread the initial post that OP made.

Code 43 is NOT the same issue that we are having!

Woulc you please be so kind to confirm that you understand our issue and that it is separate from the one you posted.

kind regards.

Crisp